Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So I still have to finish the core implementation and documentation, not to mention the other 75% of planned features, but as it is, the
OIclass has been universalized as a library tool for using and manipulating controller sources for the robot. There are a few methods that are missing documentation, and a few without bodies... Those I will finish within the next day. To use the API all you need to do is create a class that extends the newOIclass, which by the way will be renamed and moved into it's own package, and use that new class as the spot for all controller related affairs. Just as a note, during construction, theOIlibrary automatically initializes itself meaning that it will register and initialize all of the controllers before hand, so you don't actually have to do anything other than extend the class to create all of the controllers.Oh and another thing to take note of is that, the classes that previously directly interacted with the
OIclass are all broken because of a number of reasons:masterrepositoryOIlibrary is now anpublic abstract classmeaning that you must extend it to initialize / construct itOIlibrary out of it's package, nor did I rename it appropriately or at all for that matter, so as this branch currently stands, there is noOIclass.Steps for branch merging:
OICLASS INTO ANOTHER BRANCH AND DELETE THIS BRANCH, THAT IS NOT HOW GITHUB WORKS.testingbranch, for the new library tools by creating a new package, somewhere along the lines of "src.org.team4716.lib"OIclass into the same package in thetestingbranch as thebuttonifybranch, and then rename it appropriately and move it to the new package.buttonifybranch if it wasn't already done automatically.